BBS in a Box 4

home *** CD-ROM | disk | FTP | other *** search

/ BBS in a Box 4 / BBS in a Box - Macintosh - Volume IV (January 1992) (BBS in a Box).iso / Files / Tele / P / Power.cpt / Power / READ ME! / READ ME!

Wrap

Text File | 1988-11-19 | 16.0 KB | 325 lines | [APPL/LETR]

*************************************************************************** *************************************************************************** These procedures are the creation of Stephen Sayer and are meant to be distributed free of charge except where normal online charges would apply. You guys all know what this means. Don't sell my procedures to anyone or otherwise compromise my rights to these procedures. Future versions may be released as shareware and a registration fee will then be required for user support and upgrades. *************************************************************************** *************************************************************************** Welcome to Power! This is an updated release version (1.0) of Power. There may be a couple of bugs, but I tested it enough to release it so here you go. See the 1.0 release notes at the end of these docs. I will need to hear feed back from you to improve Power, so, drop me a line. E-Mail is fine too. I'm on GEnie, s.sayer1, MTS:UB at UofM, Sephen Sayer, and on several different bulletin boards across the Telenet network. I may even be on your local BBS! You can also find me very regularly on the MacTechnics BBS in Ann Arbor, MI, if you are a member of that fine organization. You should have the following files in the Power folder: 1200 10180 RSE1 SCOT Mon, Nov 7, 1988 2400 10180 RSE1 SCOT Mon, Nov 7, 1988 300 10180 RSE1 SCOT Mon, Nov 7, 1988 A.PROC 1243 RREP SCOT Sun, Nov 13, 1988 AZPHO.PROC 488 RREP SCOT Sun, Nov 13, 1988 C.PROC 1089 RREP SCOT Sun, Nov 13, 1988 CACOL.PROC 488 RREP SCOT Sun, Nov 13, 1988 CAGLE.PROC 488 RREP SCOT Sun, Nov 13, 1988 CALAN.PROC 488 RREP SCOT Sun, Nov 13, 1988 CAOAK.PROC 488 RREP SCOT Sun, Nov 13, 1988 CAPAL.PROC 488 RREP SCOT Sun, Nov 13, 1988 CASAD.PROC 488 RREP SCOT Sun, Nov 13, 1988 CASAN.PROC 488 RREP SCOT Sun, Nov 13, 1988 CASFA.PROC 488 RREP SCOT Sun, Nov 13, 1988 CASJO.PROC 488 RREP SCOT Sun, Nov 13, 1988 CC.PROC 507 RREP SCOT Sun, Nov 13, 1988 CG1.PROC 1097 RREP SCOT Sun, Nov 13, 1988 CG2.PROC 1100 RREP SCOT Sun, Nov 13, 1988 CODEN.PROC 488 RREP SCOT Sun, Nov 13, 1988 Configure Power.PROC 1857 RREP SCOT Mon, Nov 14, 1988 CP.PROC 2134 RREP SCOT Sun, Nov 13, 1988 CTHAR.PROC 488 RREP SCOT Sun, Nov 13, 1988 DC.PROC 1107 RREP SCOT Sun, Nov 13, 1988 DCWAS.PROC 488 RREP SCOT Sun, Nov 13, 1988 FLMIA.PROC 488 RREP SCOT Sun, Nov 13, 1988 FLTAM.PROC 488 RREP SCOT Sun, Nov 13, 1988 GAATL.PROC 488 RREP SCOT Sun, Nov 13, 1988 GC.PROC 2164 RREP SCOT Sun, Nov 13, 1988 GT.PROC 890 RREP SCOT Sun, Nov 13, 1988 HU.PROC 607 RREP SCOT Mon, Nov 14, 1988 ILCHI.PROC 488 RREP SCOT Sun, Nov 13, 1988 MABOS.PROC 488 RREP SCOT Sun, Nov 13, 1988 MIDET.PROC 488 RREP SCOT Sun, Nov 13, 1988 MNMIN.PROC 488 RREP SCOT Sun, Nov 13, 1988 MOKAN.PROC 488 RREP SCOT Sun, Nov 13, 1988 MOSLO.PROC 488 RREP SCOT Sun, Nov 13, 1988 NCRTP.PROC 488 RREP SCOT Sun, Nov 13, 1988 NJNEW 652 TEXT McSk Sun, Nov 13, 1988 NJNEW.PROC 488 RREP SCOT Sun, Nov 13, 1988 NYNYO.PROC 488 RREP SCOT Sun, Nov 13, 1988 OHCLV.PROC 488 RREP SCOT Sun, Nov 13, 1988 ORPOR.PROC 488 RREP SCOT Sun, Nov 13, 1988 PAPHI.PROC 488 RREP SCOT Sun, Nov 13, 1988 PM 7650 RRM1 SCOT Sun, Nov 13, 1988 READ ME! 22170 APPL LETR Mon, Nov 14, 1988 TXDAL.PROC 488 RREP SCOT Sun, Nov 13, 1988 TXHOU.PROC 488 RREP SCOT Sun, Nov 13, 1988 UTSLC.PROC 488 RREP SCOT Sun, Nov 13, 1988 WASEA.PROC 488 RREP SCOT Sun, Nov 13, 1988 WIMIL.PROC 488 RREP SCOT Sun, Nov 13, 1988 You should also have the M folder in the Power folder. In the M folder you will find these macro key files: NJNEW 7650 RRM1 SCOT Sun, Nov 13, 1988 PHS 7650 RRM1 SCOT Sun, Nov 13, 1988 PHS2 7650 RRM1 SCOT Sun, Nov 13, 1988 PLS 7650 RRM1 SCOT Sun, Nov 13, 1988 PLS2 7650 RRM1 SCOT Sun, Nov 13, 1988 PMS 7650 RRM1 SCOT Sun, Nov 13, 1988 PMS2 7650 RRM1 SCOT Sun, Nov 13, 1988 Anyway here's how to Power up. First make sure that you put the Power folder in the root directory of your HFS disk. Sorry about that but Red Ryder has serious problems with Path/File names that are too long for it to digest properly (urp!). Second make sure all of the Macro files, except PM, are in a folder within the Power folder titled M (that's right, just M, no spaces, no anything else, just M!). Now your ready to start. First initiate the Configure Power.PROC from within Red Ryder. You will need to enter your PC Pursuit ID# & Password, the dialing commands for 300, 1200, and 2400 baud access numbers for your area, a password to use to protect Power from unauthorized use, and then you will need to find the Power folder. As soon as the selection box to find the Power folder appears, it will already be in the Power folder, so you will merely need to click Select (but check just to make sure it is in the right place). Upon completion of the Configure Power.PROC, you might note that there is a new procedure which has been compiled called Power.PROC. This is an encrypted Red Ryder procedure file, so it should be fairly tamper proof. If you find that you have made a mistake in entry during the Configure Power.PROC, you should first delete the Power.PROC file then intitiate Configure Power.PROC again. You will need to enter all of the information again of course. You should also do this if you move Power to another location on your disk. Configure Power.PROC did one other thing also. It loaded the PM macro file which is what you will use to start Power. There are three buttons in this macro set. You will need to attach them to their proper procedure files. Here's how... Select Edit Macro Keys from the Edit menu. Click the Edit button then the Get Procedure File button. Then select the Power.PROC file in the selection box. Next, click Save then select the #4 Macro in the 1st set and choose Edit again. This time 'Get Procedure File' C.PROC and 'Save.' Similarly edit the #9 macro in the 1st set. Now click Done and save the Macros to the Power folder as PM. Go ahead and replace the old PM (Red Ryder will ask you if that's what you want to do). Now that your linked to the Power.PROC, you're ready to load some of the PC Pursuit cities into the arsenal. I have created some macro key files that will automatically attempt to connect with a remote PC Pursuit city. You will need to do a little work first though. In the M folder, you will find the macro files... NJNEW (for BBSs in the NJNEW area: a template...) PHS (High Speed/2400 macros, set 1) PHS2 (High Speed/2400 macros, set 2) PLS (Low Speed/300 macros, set 1) PLS2 (Low Speed/300 macros, set 2) PMS (Medium Speed/1200 macros, set 1) PMS2 (Medium Speed/1200 macros, set 2) These files have buttons in place for their intended functions. You will have to link them to the .PROC files they activate. Load each one in turn, while in Red Ryder and Edit all of the buttons that are present. The macro buttons should be assigned to the following .PROC files by using Get Procedure File to locate the procedure for that button as illustrated by this list. BUTTON => .PROC FILE ------ ---------- Call Pursuit Power.PROC Capture Text C.PROC End Capture CC.PROC Pursuit BBS * no procedure file necessary * The City buttons are easier to explain. example: BUTTON => .PROC FILE ------ ---------- GAATL:404 GAATL.PROC MABOS:617 MABOS.PROC NYNYO:212:718 NYNYO.PROC Do you see a pattern emerging here? I thought you would. Granted, there are a lot of buttons on some of those macro files, but it's really easy to do once you get going. Also if you don't use Pursuit at some speed, for example 300 baud, you don't need to link the macro files for that speed if your not going to use them (in our example the files PLS & PLS2 as shown above). You don't even have to link the city's that you don't use, but I'll bet you'll find yourself calling a lot more places once you start using Power. So load up all you can handle, remembering that I did the hardest part of this for you, and you'll get through it with few, if any, problems. Be sure to save all of these macro files with their original names in the M folder (except PM, as noted),or Power will not work properly. Now, at long last, you're ready to begin. Load the PM macro file again. Now press the Call Pursuit macro button and enter your password if you decided to use one. You will be prompted to choose what speed to connect at, then you will be connected. A note to 2400 baud users: You know how weird some of the 2400 baud access #'s can be sometimes, so when you see the "CONNECT 2400" message from your modem you may need to give the return key a few taps to get things going. Other speeds appear to work just fine. I will continue to work on this problem. You may have noticed that there is now a new item called Power in the menu bar. Take a look at the choices. "About..." is pretty self explanatory, "Get Telenet" sends an @ character to return to Telenet control, "Disc. City" sends the D command telling Telenet to disconnect from the remote city, "Hang Up" will send HANGUP to the host then hang up the phone and exit Power, "City Group 1" & "City Group 2" will toggle the macro files with the cities on them according to what speed your connected at. You will notice that there are no cities listed on the PHS2 or the PLS2 macro files. These were added for future expansion if necessary. All of the menu commands are situation sensitive in that a menu command is only available when it is appropriate. Hang Up is your panic button if you get into trouble. You must use the buttons though to stay in sync with their activation and deactivation. So try to avoid entering these commands manually. The payoff is that your macro files will be loaded automatically and you won't have to sit there entering those ridiculous strings over and over again manually. When you click on a city to call, the procedure will ask you how many times you would like for it to attempt a connection at whatever city was selected (it just occured to me to show the name of the city in that dialog box, look for that in the future versions). It will then go about it's task until either connected or it has tried the specified number of times (or if an error condition exists). When it beeps once it means that a CONNECTED message was received and you are ready to dial out. If it beeps twice, no CONNECTED message was received or there is an error condition. In any case don't panic if it beeps twice. Just select the city again, or another city, and try some more. You will later want to add dialing commands for your regular BBS contacts in different cities by creating macro files with the template, NJNEW macro file. Just name the macro file in all caps with the name of the Pursuit city code, like NJNEW. Later I may be releasing a bunch of these city macro files with the corresponding Red Ryder Host BBSs loaded already for those who have helped significantly with the development of Power through beta testing or contributions. When it comes time to add more PC Pursuit cities you will find the text file NJNEW is your template to do that. All you need to do is open NJNEW with a text editor of Red Ryder's preference and then "Save As..." the name of the Pursuit city, i.e. MABOS. Then swap the same name with the name NJNEW in the procedure file (remember all caps). Then close the file, link it to the appropriate connection speed (baud rate) macro file and it's ready to use. That's about all I can say about this so far except that with your help & suggestions I will try to improve upon Power and possibly release a related procedure set, codename Ultima. This one will allow one more wide reaching control of non Pursuit BBSs, thus integrating your telecommun- ications atmosphere. In future versions I will probably put the Capture Text & the End Capture commands in the Power menu, unless someone has strong objections. You might also notice that these two procedures (C.PROC & CC.PROC) work independently of Power's other procedures, so use them with your regular array of procedures and macro keys. The two points to remember are that C% carries a value that is tested by End Capture (CC.PROC) to determine if a text capture was started by Capture Text C.PROC, where; 0=Capture off, 1=Capture on). Also the String Variable, N$, contains the name of the Host System in my procedures, so if there is a string in N$, the procedure will first offer to capture text as the Host System's name with the current month & day according to your Mac's setting. If you find these procedures useful, wait 'til you see how great they are for all of your regular BBS'ing! If you have problems, comments, questions, tips, or just want to rap, get in touch... I can be snail mailed at: Stephen Sayer 4764 Washtenaw #C3 Ann Arbor, MI 48108-1425 I can be E-Mailed on: GEnie, s.sayer1 MTS:UB, Stephen Sayer EEE's BBS in New Jersey MacTechnics BBS in Ann Arbor, MI Thanks a lot in advance for any assistance you can offer toward the refinement and enhancement of Power. Remember you get what you pay for! Have A Great Time! Stephen Sayer aka: Electric Eye, Grinder, MiG Eater... Release Note ____________ Upgrade note 11/19/88: version 1.0b to 1.0 This copy of Power includes a bug fix that yielded a compile error when one chooses to use no password during the Configure.PROC. Thanks very much to William Marriott for pointing out this problem. This and a couple of small changes makes this version 1.0 with 1.1 to be released before the end of the year (I hope!). I would also like to mention here that it is possible to avoid having to link the macro buttons to their procedures if you put the Power folder on a disk named New Stuff and run the configuration and subsequently the Power procedure itself from there. Sorry about the difficulties any one had with the password thing. If you are reading this as part of the Power upgrade kit, or already have a copy of Power, simply replace the Configure.PROC & the CP.PROC in the Power folder with the new versions included here. You will be able to choose to use no password once these are installed. Thanks for using Power! Stephen Sayer